I was able to find a solution with some help from ChatGPT. Since I don't care about debugging anything related to the problem library, I decided to strip out the debug info from the offending file using the command: strip -S -x POSSDKForIOSLIB.a

OK, looking closer I see that the po command I issued did apparently produce an output... The very last line ends with: ... Rebuilding the project will regenerate the needed module files.7 and I had typed a "7" into the input field. So apparently every expression I evaluate is going to prepend a couple pages of irrelevant warnings to the output. It looks like Xcode 16 is turning on some LLDB warning output that was previously suppressed. I'm searching for a way to reduce the warning level, but haven't found it yet.

Thank you so much for your reply Quinn. I see where you're coming from, and I'll spend a little time reading up on the links you provided. The problem I'm having is that Xcode 15.2 gave me no issues with this, and now all I'm trying to do is evaluate local properties and UIKit types, and nothing works anymore. So something that did not cause a problem before is making it nearly impossible to debug. I would understand if this occurred while trying to inspect a type provided by this third-party library, but I'm just trying to read the value of an input control.

Hello, is this getting any attention? How can we escalate this? iOS 17 has broken a key feature in our product, and we've been unable to find a work-around.

I think the best option is to reproduce in the app store version. The app is Lineskip POS from LineSkip Inc. The app's Apple ID is 1051522633. Sign in is required. I'll assume you can use the account and password provided for App Review. If not, please let me know how I can get you the credentials. Steps to reproduce: Add an item to the cart (select By the Slice / Pepperoni) Tap the Pay & Send button Tap "Split Check" This should result in a crash.